Chip: 2005 Utilities/CHIP Utilities 2005/CHIP Utilities 2005.iso/dosapps/freedos/help/ctmouse.en

Text File | 2002-08-31 | 11.4 KB | 261 lines

CuteMouse driver v1.9. Copyright (c) 1997-2002 Nagy Daniel
Release date: 2002-05-01

CuteMouse v1.9 (English) ctmouse.exe
Also available is CuteMouse v2.0alpha (English) ctmouse2.exe


License:
--------

CuteMouse is released under the GPL license. For further information
please read the COPYING file.


Description:
------------

CuteMouse is a mouse driver which supports many mouse protocols, serial
and PS/2. It can search for serial mice at all COM ports or only at a
specified port.

An important CuteMouse feature is its small memory footprint: the TSR part
occupies less than 3.5K. CuteMouse can also install itself in upper memory
when available without requiring external utilities such as DOS 'lh'
command.

CuteMouse supports cursor drawing in all standard graphics and text modes
with any screen size. These are automatically detected whenever the video
mode or the screen size is changed or reset functions are called.

You can subscribe to the CuteMouse discussion group at the official
homepage http://cutemouse.sourceforge.net or by sending an empty letter to
<[e-mail]>.

CuteMouse is part of the FreeDOS project at http://www.freedos.org


Details:
--------

CTMOUSE supports standard Mouse Systems, Microsoft and Logitech serial and
PS/2 protocols. When searching for a connected mouse, the PS/2 port is
checked first, then all COM ports are scanned. Option /S, whose syntax is
described in the help screen, disables PS/2 support and can specify the
COM port to be checked for a mouse connection and its IRQ line; option /P
disables serial protocols. If option /S is present in the command line,
but PS/2 support is also required, then option /P must also be present.

If COM port number is not specified with /S option, then CTMOUSE searches
all COM ports. If IRQ line is not specified with /S option, then the
default IRQ line value is IRQ4 for COM1/3 and IRQ3 for COM2/4. In the
future, when IRQ autodetection will be added, then there will be no
explicit assumption.

By default, a PS/2 mouse is searched for before a serial mouse, but option
/V reverses this. Option /V can be useful, for example, on notebooks with
a built-in PS/2 pointing device to enable use of a serial mouse, when
attached, by causing CTMOUSE to look for a serial mouse before checking
the PS/2 device. Using option /Y (see below) also may be required along
with /V. Note: option /V enables both serial and PS/2 protocols, so using
options /P and /S without arguments along with /V in the command line is
meaningless.

For serial mice, CTMOUSE searches all COM ports (or at the port specified
by option /S) for an attached Microsoft or Logitech mode mouse. If no such
mouse is found then CTMOUSE installs at the first existing (or specified)
COM port for a Mouse Systems mode, whether a mouse is there or not. (This
is because Mouse Systems protocol defines no detection sequence). Option
/Y in the command line disables Mouse Systems protocol support and
prevents driver installation if no Microsoft or Logitech mode mouse is
found. Note: option /Y forces serial mouse search, but, unlike option /S,
doesn't disable PS/2 support.

Both PS/2 and plain Microsoft protocols assume two button mice but option
/3 in the command line can be used to enable the middle button if one is
present.

WARNING: when the middle button of a plain Microsoft mouse is enabled,
pressing left or right button along with the middle button can cause
"middle button state triggering" - i.e. when the middle button is pressed
the driver thinks it is released and vice-versa. This is a peculiarity of
the Microsoft protocol and can't be changed. If button triggering occurs
simply press the left or right button along with the middle button once
again to clear the problem.

CTMOUSE supports 9 fixed resolution levels plus auto resolution, which
define the relationship between cursor and mouse movement - the higher the
resolution level, the further the cursor moves for a given mouse movement.
Resolution level 1 or small mouse movements at any resolution provides a
direct relationship between cursor and mouse movement, which enables
precise screen positioning even at the highest resolution levels. Larger
mouse movements and higher resolution levels are multiplied together to
determine the cursor movement, enabling rapid cursor movements across the
screen for relatively small mouse movements.

Auto resolution means dynamic resolution change, where the faster the
mouse moves, the greater the resolution by which the mouse movements are
multiplied, giving the cursor a nonlinear acceleration. Option /R, whose
syntax is described in the help screen, allows the preferred resolution
level to be specified for each direction.

If installing from low memory, CTMOUSE attempts to move itself into upper
memory (UMB) if there is a suitable free UMB block and option /W is not
used. With option /W any external utility can be used to install CTMOUSE
at a specific location. Subsequent CTMOUSE runs simply reset the resident
part to the new command line options, unless the mouse is not found or
option /B or /N is used.

When installing, CTMOUSE also ignores and hides any present mouse services
unless option /B is used. Option /U in command line can be used to unload
the resident part of CTMOUSE unless driver interrupts have been
intercepted by another program. After successful unloading, CTMOUSE
restores mouse services that were present at installation time.

Option /B in the command line cancels CTMOUSE execution if any (including
CTMOUSE itself) mouse services are already present. With option /B CTMOUSE
will not install itself above loaded mouse drivers and will not reset the
resident part to new command line options.

On the contrary, option /N forces to load new TSR even if CTMOUSE is
already loaded - without this option CTMOUSE will only reset loaded
resident part. In cases where mouse services are provided by any other
driver or are not present at all, CTMOUSE loads new TSR even without
option /N - see table below:

options        no services    other driver    loaded CTMOUSE
-------        -----------    ------------    --------------
/B        load CTMOUSE    do nothing    do nothing
<default>    load CTMOUSE    load CTMOUSE    update resident part
/N        load CTMOUSE    load CTMOUSE    load new CTMOUSE

Option /N is useful for batch files, which load CTMOUSE at start and
unload it at the end.

For each event CTMOUSE returns an appropriate exit code which can be used
in "if errorlevel" statements in batch files:

    0 - PS/2, Microsoft or Logitech mouse found and CTMOUSE installed;
    unload successful;
    /? option used
    1 - CTMOUSE installed for Mouse Systems protocol;
    unload failed - CTMOUSE not installed
    2 - resident part switched to PS/2, Microsoft or Logitech protocol;
    unload failed - driver interrupts intercepted
    3 - resident part switched to Mouse Systems protocol
    4 - mouse services already present (returned for option /B only)
    5 - mouse not found;
    invalid option used

Along with options /B and /N, this enables creation of complex and
intelligent batch files. For example, the following batch can be used to
run a program that requires mouse services to be present:

    ctmouse/n/y>nul
    if errorlevel 5 echo Mouse not found!
    if errorlevel 5 goto end
    <program> %1 %2 %3 %4 %5 %6 %7 %8 %9
    ctmouse/u>nul
    :end

Option /B can be used to manually specify a mouse search sequence. In the
following example, CTMOUSE is installed by the first command that finds a
mouse and the following commands will have no affect on the resident part:

    ctmouse/b/s4/y>nul
    ctmouse/b/p/y>nul
    ctmouse/b/s2/y>nul

A help screen with all option descriptions can be obtained with the /?
command line option.

The CuteMouse package also includes utility to detect COM ports (COMTEST)
and serial protocol analyzer (PROTOCOL). PROTOCOL shows how mice work and
what they send to the computer for each action. PROTOCOL can even decipher
information sent by PnP mice. All output goes through DOS functions and
can be redirected to a file for subsequent analysis or sending to someone
else.


Compiling:
----------

To assemble the English version of the driver use TASM (or any compatible
assembler) and any linker that can produce a COM file from OBJ files:

    copy ctm-en.msg ctmouse.msg
    tasm /m @asmlib.cfg ctmouse.asm
    tlink /t /x ctmouse.obj,ctmouse.exe
    com2exe -s512 ctmouse.exe ctmouse.exe

To assemble the serial protocol analyzer:

    tasm /m @..\asmlib.cfg protocol.asm
    tlink /t /x protocol.obj

To compile or delete temporary files, the MAKE utility also can be used
(see makefile).


Known problems:
---------------

Symptom: if mouse is moved when Works 2.0 for DOS or Word 5.5 for DOS
redraws screen in graphics mode then some parts of screen are garbaged.
Cause: these programs don't hide mouse cursor while drawing on screen
and/or don't use EGA RIL API when changing video adapter registers.
Solution: correct these program's code; don't move mouse while screen is
being redrawn; future version of CuteMouse will probably read VGA adapter
registers directly.

Symptom: under Windows 3.1 after mouse reset (INT 33/0000) graphics mouse
cursor shifted by one pixel right/down. Cause: Windows traps INT 33 call
and for reset function additionally calls text and graphics cursor define
functions with [-1,-1] hot spot. Solution: call INT 33 not through 'INT'
instruction but through 'PUSHF/CALL FAR' sequence; probably there exists
some API which CuteMouse can use in future to interact with Windows
directly.

Symptom: sometime under Windows 3.1 graphics cursor has black box shape.
This also sometime happens after switching between tasks windows. Cause:
probably caused by Windows bug when Windows incorrectly redefine cursors
at the time of task switching. Solution: restart graphics application or
try to switch back and forth between tasks again; probably there exists
some API which CuteMouse can use in future to interact with Windows
directly.

Symptom: when CuteMouse is installed then, unlike Microsoft Mouse driver
8.2, mouse doesn't work in windowed DOS box of Windows 3.1. Cause: most
probably Microsoft Mouse driver uses unpublished API to interact with
Windows. Solution: unknown at this moment.

Symptom: CuteMouse will fail to detect PS/2 mice under Windows 9x/ME.
Cause: it seems that Windows is unwilling to let a DOS application have
access to the PS/2 device services. Solution: unknown at present.


Credits:
--------

- Arkady V.Belousov <[e-mail]>: many bugfixes, optimizations and features
- Alain Mouette <[e-mail]>: many ideas and message files
- Frank Pruefer <[e-mail]>: documentation proofreading
- Jason Burgon <[e-mail]>: bugfixes, features, advices
  about interrupts handling consistency
- Joergen Ibsen / Jibz <[e-mail]>: author of aPACK (an excellent
  executable packing program); some advices about managing executables
- Matthias Paul <[e-mail]>
- Mike Millen <[e-mail]>: documentation proofreading
- Robert Riebisch <[e-mail]>: mode 13h positioning bugfix
- Fernando Papa Budzyn: self-loadhigh capability
- Martin <[e-mail]>: optimizations
- Paul Schubert: much faster PS/2 codes
- All who helped me with ideas and codes


Contacts:
---------

mailto:[e-mail]
http://cutemouse.sourceforge.net